[SPARK-50903][CONNECT] Update plan cache entries after analysis #49584
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Update the plan cache after a plan is analyzed.
Why are the changes needed?
The session local plan cache storing unanalyzed logical plans without updating them causes those plans to be repeatedly analyzed, causing performance degradation.
To be specific, a common usage pattern of the session local plan cache (100%) is,
where an unanalyzed plan may be cached during transformation, and Dataset.ofRows analyzes the unanalyzed plan. This leads to a situation where the same query may hit the cache which in turn returns an unanalyzed plan, and Dataset.ofRows again analyzes the same plan.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
testOnly org.apache.spark.sql.connect.service.SparkConnectSessionHolderSuite
Was this patch authored or co-authored using generative AI tooling?
No.